Memory management system supporting deletion of transient objects

ABSTRACT

One embodiment of the present invention provides a system for compacting memory within a computing device, wherein the computing device supports transient objects, having a persistent portion stored in a writeable non-volatile memory, and a transient portion stored in a volatile memory. During the compaction process, the system resets the volatile memory so that information in the volatile memory is deleted. Next, the system scans through a list of objects. For each transient object encountered in the list of objects, the system allocates space for the transient object in the volatile memory. The system also updates the persistent portion of the transient object, if necessary, to specify a new location in volatile memory for the transient portion of the transient object.

RELATED APPLICATIONS

The subject matter of this application is related to the subject matterin a co-pending non-provisional application by Saqib J. Ahmad filed onthe same day as the instant application, entitled, “Method and Apparatusfor Deleting Objects From Memory within a Smart Card,” having SerialNumber TO BE ASSIGNED, and filing date TO BE ASSIGNED (Attorney DocketNo. SUN-P7670-EKL).

The subject matter of this application is also related to the subjectmatter in a co-pending non-provisional application by the same inventoras the instant application, filed on the same day as the instantapplication, entitled, “Memory Management System Supporting ObjectDeletion in Non-volatile Memory”, having Serial Number TO BE ASSIGNED,and filing date TO BE ASSIGNED(Attorney Docket No. SUN-P7698-EKL).

BACKGROUND

1. Field of the Invention

The present invention relates to the process of managing memory in acomputer system. More specifically, the present invention relates to amethod and an apparatus for freeing memory within a computing device,such as a smart card, which includes both volatile and non-volatilememory.

2. Related Art

Dramatic advances in computer technology presently make it possible tointegrate a significant amount of computing power onto a “smart card”.This increased computing power enables smart cards to support largenumbers of applications. However, unlike conventional computing systems,smart card-based computing systems do not presently provide a mechanismfor reclaiming memory occupied by objects that are no longer in use.This process of reclaiming unused memory is often referred to as“garbage collection”.

Garbage collection can be performed in conventional computing systemsusing a number of well-known techniques. However, smart card-basedcomputing systems are different than conventional computing systemsbecause objects can reside in writeable non-volatile memory, such aselectrically erasable programmable read only memory (EEPROM) or flashmemory. (Within this specification the term “EEPROM” refers to both“EEPROM” and “flash memory.”)

Existing garbage collection techniques are not suitable for EEPROMbecause individual memory elements in EEPROM can only be written to alimited number of times. Hence, existing garbage collection techniques,which operate by frequently marking objects in memory, can dramaticallyreduce the life expectancy of EEPROM. Moreover, the process ofperforming write operations to EEPROM is typically very slow, which cansignificantly degrade system performance.

Smart cards often contain a small amount of volatile random accessmemory (RAM), which does not suffer from the above-described problems ofwriteable non-nonvolatile memory. However, the amount of RAM is oftenextremely limited. Hence, it is not possible to store a complete imageof EEPROM in RAM; even a bitmap representing blocks of EEPROM would takeup too much space in RAM.

The garbage collection process operates by first deleting unused objectsfrom memory. Once the objects are deleted, the memory space formerlyoccupied by the objects must somehow be reclaimed. In conventionalcomputing systems, this reclamation process is typically accomplished byperforming a compaction operation to eliminate “holes” in memory thatarise as a consequence of deleting objects. However, a compactionoperation typically involves rewriting a significant portion of memory,which tends to reduce the life expectancy of the EEPROM.

Hence, what is needed is a method and an apparatus for reclaiming memorywithout requiring the large number of write operations involved inperforming a compaction operation.

Furthermore, in computing devices that include both EEPROM and RAM, itis possible to define “transient objects,” which include a portiondefined in EEPROM and a portion defined in RAM. In order to support suchhybrid objects, what is needed is a method and an apparatus thatreclaims memory used by these hybrid objects.

SUMMARY

One embodiment of the present invention provides a system for compactingmemory within a computing device, wherein the computing device supportstransient objects, having a persistent portion stored in a writeablenon-volatile memory, and a transient portion stored in a volatilememory. During the compaction process, the system resets the volatilememory so that information in the volatile memory is deleted. Next, thesystem scans through a list of objects. For each transient objectencountered in the list of objects, the system allocates space for thetransient object in the volatile memory. The system also updates thepersistent portion of the transient object, if necessary, to specify anew location in volatile memory for the transient portion of thetransient object.

In a variation on this embodiment, the compaction can occur during aninitialization of the computing device, or during an initialization of anew application on the computing device.

In a variation on this embodiment, prior to resetting the volatilememory, the system determines if compaction is needed by checking stateinformation in the writeable non-volatile memory, wherein the stateinformation indicates whether a transient object has been deleted. In afurther variation, the state information includes separate stateinformation for different pools of volatile memory, thereby allowingcompaction of specific pools of volatile memory, without having tocompact all of the volatile memory. Note that a heap in volatile memorycan be divided into a number of pools.

In a variation on this embodiment, the list of objects includes: a listof transient objects in a clear-on-reset heap within the volatile memorythat are to be cleared on reset of the computing device; and a list oftransient objects in a clear-on-deselect heap within the volatile memorythat are to be cleared when an application running on the computingdevice is deselected.

In a variation on this embodiment, the writeable non-volatile memory caninclude: electrically erasable read only memory (EEPROM), flash memory,or a magnetic memory device.

BRIEF DESCRIPTION OF THE FIGURES

FIG. 1 illustrates a smart card in accordance with an embodiment of thepresent invention.

FIG. 2 illustrates a transient object in accordance with an embodimentof the present invention.

FIG. 3 illustrates memory heaps and object tables in accordance with anembodiment of the present invention.

FIG. 4 illustrates a free segment table in accordance with an embodimentof the present invention.

FIG. 5 is a flow chart illustrating the process of freeing a segment ofmemory from writeable non-volatile memory in accordance with anembodiment of the present invention.

FIG. 6 is a flow chart illustrating the process of compacting RAM thatcontains portions of transient objects in accordance with an embodimentof the present invention.

DETAILED DESCRIPTION

The following description is presented to enable any person skilled inthe art to make and use the invention, and is provided in the context ofa particular application and its requirements. Various modifications tothe disclosed embodiments will be readily apparent to those skilled inthe art, and the general principles defined herein may be applied toother embodiments and applications without departing from the spirit andscope of the present invention. Thus, the present invention is notlimited to the embodiments shown, but is to be accorded the widest scopeconsistent with the principles and features disclosed herein.

The data structures and code described in this detailed description aretypically stored on a computer-readable storage medium, which may be anydevice or medium that can store code and/or data for use by a computersystem. This includes, but is not limited to, magnetic and opticalstorage devices such as disk drives, magnetic tape, CDs (compact discs)and DVDs (digital versatile discs or digital video discs), and computerinstruction signals embodied in a transmission medium (with or without acarrier wave upon which the signals are modulated). For example, thetransmission medium may include a communications network, such as theInternet.

Smart Card

FIG. 1 illustrates a smart card 100 in accordance with an embodiment ofthe present invention. Smart card 100 can generally include any type ofminiature computing device, such as may be located within identificationcards, client loyalty cards, electronic wallets and cellular telephones.However, note that the present invention is not meant to be limited tosmart cards, and can generally be applied to any type of computingdevice or computer system that stores objects in writeable non-volatilememory and/or volatile memory.

Smart card 100 contains a computational engine 126, which includescircuitry for performing computational operations. Smart card 100 alsocontains a number of different types of memory, including random accessmemory (RAM) 120, electrically erasable programmable read-only memory(EEPROM) 122 and read-only memory (ROM) 124. In general, RAM 120 caninclude any type of volatile random access memory; EEPROM 122 caninclude any type of writeable non-volatile memory, such as EEPROM, flashmemory, or magnetic memory; and ROM 124 can include any type ofread-only memory.

RAM 120 is used to store various data items and data structures. Forexample, as illustrated in FIG. 1, RAM 120 can contain portions ofobjects 112, 115 and 113. Note that objects 112, 113 and 115 are“transient objects” that include a persistent portion stored in EEPROM122, and a transient portion stored in a RAM 120.

ROM 124 includes a virtual machine 108, such as the JAVA virtual machinedeveloped by SUN Microsystems, Inc. of Santa Clara, Calif. Note thatapplications written in a platform-independent programming language,such as the JAVA programming language, can be executed on virtualmachine 108.

ROM 124 also contains a number of applications, 104 and 105, whichprovide services for clients accessing smart card 100. Otherapplications, such as application 106, can be located in EEPROM 122.Further applications (not illustrated) may be located in both ROM 124and EEPROM 122.

ROM 124 also includes a card manager 102, which contains code formanaging the execution of applications on smart card 100. For example,suppose a client 110 wishes to access a service provided by one of theapplications 104-106 on smart card 100. Client 110 first communicateswith card manager 102 (step A). Card manager 102 puts client 110 incontact with an application 104 (step B). This allows client 110 tocommunicate directly with application 104 (step C). Note that cardmanager 102 can also delete objects from memory.

RAM 120 and EEPROM 122 and contain a number of objects 112-114, whichare accessed by applications 104-105. More specifically, application 104accesses object 112, application 105 accesses objects 113 and 114, andapplication 106 accesses object 114. Other objects 115-116 (that havebecome unlinked) are not referenced by any application. It is desirableto delete these unreferenced objects to free up memory space in RAM 120and EEPROM 122.

Transient Object

FIG. 2 illustrates a transient object 200 in accordance with anembodiment of the present invention. Transient object 200 includes apersistent portion in EEPROM 122, which contains an object header 202.Transient object 200 also includes a transient portion 210 in RAM 120,which contains data fields for the object.

Object header 202 contains various fields, including an object typefield 203. Object type field 203 can specify, for example, whethertransient object is a “clear-on-reset” object, which is cleared uponreset of the computing device, or a “clear-on deselect” object, which iscleared when an application running on the computing device isdeselected. Object header 202 also includes an address field 204, whichcontains the address in RAM 120 of the transient portion 210 oftransient object 200, Object header 202 also includes a size field 205,which indicates the size of the transient portion 210 of transientobject 200.

Heaps and Object Tables

FIG. 3 illustrates memory heaps and object tables in accordance with anembodiment of the present invention. Smart card 100 contains a number ofheaps for storing objects or portions of objects.

More specifically, FIG. 3 illustrates a clear-on-reset heap 310, and aclear-on-deselect heap 312, which are both located in RAM 120.Clear-on-deselect heap 312 contains transient objects or portions oftransient objects which are cleared when an application that iscurrently running on smart card 100 is deselected. Clear-on-reset heapcontains transient objects or portions of transient objects that arecleared upon resetting of smart card 100.

FIG. 3 also illustrates an object heap 308 in EEPROM 122. Object heap308 contains both persistent objects and the persistent portions oftransient objects.

As is illustrated in FIG. 3, EEPROM 122 additionally contains a numberof tables that point to objects. More specifically, EEPROM 122 containsobject table 302, which points to all objects, including both persistentobjects and transient objects. EEPROM 122 also contains clear-on-resetobject table 304, which points to objects or portions of objects inclear-on-reset heap 310. EEPROM 122 additionally containsclear-on-deselect object table 306, which points to objects or portionsof objects in clear-on-deselect heap 312. The above-described tables canbe used during the process of deleting objects and during the process offreeing space used by deleted objects as is described below withreference to FIGS. 5 and 6.

Free Segment Table

FIG. 4 illustrates free segment table 401 in accordance with anembodiment of the present invention. Free segment table 401 is stored inEEPROM 122 and includes entries identifying free segments of memorywithin EEPROM 122. Free segment table 401 can be used during the processof reclaiming memory from object heap 308 in EEPROM 122. However, notethat in general any type of data structure for storing segmentinformation can be used for this purpose, and the present invention isnot meant to be limited to the structure illustrated in FIG. 4.

As is illustrated in FIG. 4, free segment table 401 includes one or moretable nodes, 400 and 410, which point to tables 420 and 430,respectively. More specifically, table node 400 contains a table pointerfield 402, which points to table 420. Table node 400 also contains a“number of entries” field 406, which indicates how many entries arestored in table 420. Table node 400 also contains a next pointer field404, which points to the next table node—which in FIG. 4 is table node410. Table node 410 similarly contains a table pointer field, whichpoints to table 430, as well as a number of entries field 416, whichindicates how many entries are stored in table 430. Since there are noadditional table nodes, next pointer field 414 contains a NULL value.Note that table nodes and corresponding tables are allocated as they areneeded.

Table 420 contains a number of entries, each of which specifies anaddress and a size for a free segment of memory in object heap 308. Notethat table 420 is completely full. In contrast, table 430 contains onlya single segment, and the rest of table 430 is empty.

Process of Freeing a Segment of Writeable Non-volatile Memory

FIG. 5 is a flow chart illustrating the process of freeing a segment ofwriteable non-volatile memory in accordance with an embodiment of thepresent invention. The process starts when the system receives a commandto free a given segment of memory (step 502). This command specifies thelocation of the given segment and the size of the given segment. Notethat the size of the given segment can be explicitly stated, oralternatively, can be determined from start and end addresses for thegiven segment. Also note that the segment of memory can be associatedwith either a persistent object that has been deleted from EEPROM 112,or a persistent portion of the transient object that has been deletedfrom EEPROM 112.

Note that this preceding object deletion process can involve a mark andsweep technique that marks objects in EEPROM by marking correspondingdata values in RAM. This avoids unnecessary write operations to theEEPROM, which can decrease the expected life of the EEPROM.

In one embodiment of the present invention, this command is received asa method invocation or a function call during garbage collection orapplication deletion (which includes applet deletion and/or packagedeletion).

In response to the command, the system scans through free segment table401 (step 504). During the scanning process, the system determineswhether the given segment is contiguous with any existing segments infree segment table 401 (step 506). If so, the system determines if thegiven segment bridges two existing segments (step 508). In this case,the system concatenates the given segment with the two existing segmentsinto a single segment (step 510). This is accomplished by increasing thesize of the existing segment with the lowest base address so that itcovers all three segments, and then removing the entry for the otherexisting segment from free segment table 401.

If the given segment does not bridge two existing segments in step 508,the system concatenates the given segment with the contiguous existingsegment (step 512). This involves increasing the size of the existingsegment to encompass both the existing segment and the given segment,and possibly changing the base address of the existing segment.

If at step 506, the system cannot find any contiguous segments, thesystem determines if free segment table 401 is full (step 516). If not,the system allocates a new entry in free segment table 401 for the givensegment (step 510) and initializes this entry with the address and sizeof the given segment.

On the other hand, if free segment table 401 is full at step 516, thesystem allocates an additional table to accommodate the additionalsegment (step 518). In the implementation of free segment table 401illustrated in FIG. 4, this involves allocating an additional tablenode. Next, the system allocates a new entry in free segment table 401for the given segment (step 520) and then initializes this entry withthe address and size of the given segment. At this point the allocationprocess is complete.

Note that during a subsequent allocation operation, the system allocatesa new segment from free segment table 401 using a “best fit” techniquethat allocates the smallest segment that is large enough to accommodatethe new segment. By selecting the smallest possible segment, the systemtends to keep larger segments in tact. This allows the system tosubsequently allocate larger segments if they are needed.

Process of Compacting Ram Containing Portions of Hybrid Objects

FIG. 6 is a flow chart illustrating the process of compacting RAMcontaining portions of transient objects in accordance with anembodiment of the present invention. Note that this compaction processdoes not delete existing transient objects. It merely reclaims thememory space used by transient objects that have been deleted, and atthe same time clears data stored in transient portions of transientobjects. Also note that the memory occupied by the persistent portionsof transient objects can be reclaimed using the process described abovefor persistent objects.

First, the compaction process is initiated (step 602). For example, thecompaction process can be initiated upon card initialization when smartcard 100 is first inserted into a card reader. Alternatively, thecompaction process can be initiated upon selection of a new application(applet) to be executed on smart card 100.

Next, the system determines if compaction is needed (step 604). Thisinvolves examining state information in EEPROM 122, which indicateswhether any transient objects have been deleted. This state informationcan be set by any process that deletes transient objects.

In one embodiment of the present invention, memory within RAM 120 isdivided into a number of “pools” and the state information indicateswhich pools need to be compacted. This avoids having to compact allobject memory in RAM 120 if only a single pool of memory in RAM 120needs to be compacted. If the state information indicates no compactionis needed, the process terminates. Note that a heap in volatile memorycan be divided into a number of pools.

Otherwise, the system starts the compaction process. This involvesresetting an appropriate heap in RAM 120 back to its initial state (step606). For example, if an application has been deselected, the system canreset clear-on-deselect heap 312 in RAM 120 (see FIG. 3).

Next, the system walks through the appropriate transient object table(for example clear-on-deselect object table 306 in FIG. 3) andreallocates space in RAM 120 for the transient objects that have notbeen deleted (step 608). Note that if the address of a transient objecthas changed, a pointer within the transient object's header, which islocated in EEPROM 122, is modified to point to the new address. At thispoint the compaction process is complete.

The foregoing descriptions of embodiments of the present invention havebeen presented only for purposes of illustration and description. Theyare not intended to be exhaustive or to limit the present invention tothe forms disclosed. Accordingly, many modifications and variations willbe apparent to practitioners skilled in the art. Additionally, the abovedisclosure is not intended to limit the present invention. The scope ofthe present invention is defined by the appended claims.

What is claimed is:
 1. A method for compacting memory within a computingdevice, wherein the computing device supports transient objects having apersistent portion stored in a writeable non-volatile memory and atransient portion stored in a volatile memory, the method comprising:resetting the volatile memory so that information in the volatile memoryis deleted; scanning through a list of objects, wherein the list ofobjects is stored in the non-volatile memory; and for each transientobject encountered in the list of objects, allocating space for thetransient object in the volatile memory, and updating the persistentportion of the transient object, if necessary, to specify a new locationin volatile memory for the transient portion of the transient object. 2.The method of claim 1, wherein the compaction can occur during: aninitialization of the computing device; and an initialization of a newapplication on the computing device.
 3. The method of claim 1, whereinprior to resetting the volatile memory, the method additionally involvesdetermining if compaction is needed, by checking state information inthe writeable non-volatile memory, wherein the state informationindicates whether a transient object has been deleted.
 4. The method ofclaim 2, wherein the state information includes separate stateinformation for different pools of volatile memory, thereby allowingcompaction of specific pools of volatile memory, without having tocompact all of the volatile memory.
 5. The method of claim 1, whereinthe list of objects includes: a list of transient objects in aclear-on-reset heap within the volatile memory that are to be cleared onreset of the computing device; and a list of transient objects in aclear-on-deselect heap within the volatile memory that are to be clearedwhen an application running on the computing device is deselected. 6.The method of claim 1, wherein the computing device is located within asmart card that can be part of, an identification card, a client loyaltycard, or an electronic wallet; or wherein the computing device islocated within a cellular telephone.
 7. The method of claim 1, whereinthe writeable non-volatile memory can include one of: an electricallyerasable read only memory (EEPROM); a flash memory; and a magneticmemory device.
 8. A computer-readable storage medium storinginstructions that when executed by a computer cause the computer toperform a method for compacting memory within a computing device,wherein the computing device supports transient objects having apersistent portion stored in a writeable non-volatile memory and atransient portion stored in a volatile memory, the method comprising:resetting the volatile memory so that information in the volatile memoryis deleted; scanning through a list of objects, wherein the list ofobjects is stored in the non-volatile memory; and for each transientobject encountered in the list of objects, allocating space for thetransient object in the volatile memory, and updating the persistentportion of the transient object, if necessary, to specify a new locationin volatile memory for the transient portion of the transient object. 9.The computer-readable storage medium of claim 8, wherein the compactioncan occur during: an initialization of the computing device; and aninitialization of a new application on the computing device.
 10. Thecomputer-readable storage medium of claim 8, wherein prior to resettingthe volatile memory, the method additionally involves determining ifcompaction is needed, by checking state information in the writeablenon-volatile memory, wherein the state information indicates whether atransient object has been deleted.
 11. The computer-readable storagemedium of claim 10, wherein the state information includes separatestate information for different pools of volatile memory, therebyallowing compaction of specific pools of volatile memory, without havingto compact all of the volatile memory.
 12. The computer-readable storagemedium of claim 8, wherein the list of objects includes: a list oftransient objects in a clear-on-reset heap within the volatile memorythat are to be cleared on reset of the computing device; and a list oftransient objects in a clear-on-deselect heap within the volatile memorythat are to be cleared when an application running on the computingdevice is deselected.
 13. The computer-readable storage medium of claim8, wherein the computing device is located within a smart card that canbe part of, an identification card, a client loyalty card, or anelectronic wallet; or wherein the computing device is located within acellular telephone.
 14. The computer-readable storage medium of claim 8,wherein the writeable non-volatile memory can include one of: anelectrically erasable read only memory (EEPROM); a flash memory; and amagnetic memory device.
 15. An apparatus for compacting memory within acomputing device, wherein the computing device supports transientobjects having a persistent portion stored in a writeable non-volatilememory and a transient portion stored in a volatile memory, theapparatus comprising: a resetting mechanism that is configured to resetthe volatile memory so that information in the volatile memory isdeleted; an allocation mechanism that is configured to scan through alist of objects, wherein the list of objects is stored in thenon-volatile memory; wherein for each transient object encountered inthe list of objects, the allocation mechanism is configured to, allocatespace for the transient object in the volatile memory, and to update thepersistent portion of the transient object, if necessary, to specify anew location in volatile memory for the transient portion of thetransient object.
 16. The apparatus of claim 15, wherein the compactioncan occur during: an initialization of the computing device; and aninitialization of a new application on the computing device.
 17. Theapparatus of claim 15, further comprising a mechanism that determines ifcompaction is needed, by checking state information in the writeablenon-volatile memory, wherein the state information indicates whether atransient object has been deleted.
 18. The apparatus of claim 17,wherein the state information includes separate state information fordifferent pools of volatile memory, thereby allowing compaction ofspecific pools of volatile memory, without having to compact all of thevolatile memory.
 19. The apparatus of claim 17, wherein the list ofobjects includes: a list of transient objects in a clear-on-reset heapwithin the volatile memory that are to be cleared on reset of thecomputing device; and a list of transient objects in a clear-on-deselectheap within the volatile memory that are to be cleared when anapplication running on the computing device is deselected.
 20. Theapparatus of claim 17, wherein the computing device is located within asmart card that can be part of, an identification card, a client loyaltycard, or an electronic wallet; or wherein the computing device islocated within a cellular telephone.
 21. The apparatus of claim 17,wherein the writeable non-volatile memory can include one of: anelectrically erasable read only memory (EEPROM); a flash memory; and amagnetic memory device.
 22. A means for compacting memory within acomputing device, wherein the computing device supports transientobjects having a persistent portion stored in a writeable non-volatilememory and a transient portion stored in a volatile memory, comprising:a resetting means for resetting the volatile memory so that informationin the volatile memory is deleted; an allocating means for allocatingspace for transient objects in volatile memory; and an object updatingmeans for updating a persistent portion of a transient object, ifnecessary, to specify a new location in volatile memory for thetransient portion of the transient object.